[This workshop has been rescheduled to May 12 due to French holiday on May 13th] In this hands-on workshop we will explore how to expose, document, secure and monetize your APIs using Gloo Portal and either Gloo Edge or the Istio Ingress Gateway. What is Gloo Portal? The Solo.io Gloo Portal provides a framework for managing the definitions of APIs, API client identity, and API policies on top of Istio and Gloo Edge. Vendors of API products can leverage the Gloo Portal to secure, manage, and publish their APIs independent of the operations used to manage networking infrastructure. Powered by the OpenAPI specifications, the Gloo Portal provides policy, traffic control, and a web UI for consuming APIs provided by services deployed in and outside of Kubernetes. How does it work? Gloo Portal is driven using declarative YAML configuration (Kubernetes Custom Resource Definitions), as well as by the service discovery and routing capabilities of Gloo Edge or the Istio Ingress Gateway making it the first Kubernetes-native Developer Portal of its kind. Users of the Gloo Portal upload API Documents (OpenAPI schemas) that reflect the APIs served by microservices running inside (or outside) Kubernetes. Once that is done, users can do any of the following: -Bundle individual API operations into API Products. -Publish API Products to a customizable Portal Web UI. -Expose API Products to Ingress traffic with Istio or Gloo Edge. -Set Authorization and Rate-Limiting policies on exposed API Products. In this workshop, each participant will have a dedicated environment he will be able to use to go through many hands-on labs: -Deploy several versions of a demo application -Configure API documents, API products, Environments and Portals to expose them -Customize the look and feel of the Portal -Secure the Portal